home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_1199
/
915
< prev
next >
Wrap
Internet Message Format
|
1994-08-27
|
2KB
Date: Wed, 20 Jul 1994 22:01:49 -0400 (EDT)
From: Timothy Miller <millert@undergrad.csee.usf.edu>
Subject: Amodal
To: gem-list@world.std.com
In-Reply-To: <memo.716895@cix.compulink.co.uk>
Message-Id: <Pine.3.87.9407202249.B29726-0100000@grad>
Mime-Version: 1.0
Precedence: bulk
Warwick:
]>Someone mentioned using the WM_TOPPED message for getting clicks on
]>background windows. This works for single clicks, but the signal doesn't
]>go through until the button is released, so I can't effectively work with
]>sliders and other thigs that require dragging.
]>
]>How do you do this?
]
]On older TOS's this is exactly the case - no dragging. But with WINX or
]with newer TOS versions, the BEVENT flag of a window can be set, thus
]allowing it to perform drags. Sliders generally provide paging or lining
]areas/buttons, so they are still usable via single clicks, just not as
]much as when topped.
Yeah, my sliders do paging and all the normal sorts of things. I just
sorta miss being able to drag. Oh well.
I have dialog window flags for disabled (no topping closing or
functioning of any other sort except for moving and redraw requests...
this is for when dialogs spin off child dialogs and you don't want the
user to access the parent until the child is donw), untoppable, and
background-active.
Another question to you programming guru's:
Say you have a vertical slider and you use graf_dragbox to handle
dragging of the slider. The slider ends up being two pixels thinner than
the parent and can move left and right a little. Why?
My solution was to temporarily increase its width by two.
Hey, are you guys actually going to make suggestions for me or just steal
my ideas? :)